Summary

Fixes PMAA-126: test cases created via the createTestCase MCP tool always defaulted to Medium priority, regardless of what the user/agent asked for (e.g. "Critical" or "High").

Root cause

createTestCase had no priority field in its input schema (CreateTestCaseSchema) or its TestCaseCreateRequest interface. Since the request body is built directly from those params, priority was never sent to the Test Management API, so the API applied its default (Medium).

This is not a TM API contract change — the API still accepts priority on create. Verified directly:

The API requires the Title-Case display name.

Changes

• create-testcase.ts — add priority to the schema + interface, and a normalizePriority step that resolves the input to the API-accepted display name (so critical, Critical, or high all work) before sending. On form-fields lookup failure it passes the raw value through so the backend can surface its own error.
• TCG-utils/api.ts — extract the existing default-field normalizer into a shared, exported normalizeDefaultFieldValue (sits next to fetchFormFields / projectIdentifierToId, which it depends on).
• update-testcase.ts — dedup: replace its private local copy of the normalizer with the shared import. No behavior change.

Testing

• New unit tests for normalizeDefaultFieldValue (case-insensitive matching, display↔internal name, no-match fallback).
• New implementation-level tests for createTestCase: normalized priority lands in the request body, priority omitted → not sent (preserves project default), form-fields lookup failure → raw value passed through.
• Full suite green: 178 tests pass; lint / format / tsc clean.

🤖 Generated with Claude Code